Add NetTCR dataframe input - #258
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes #255.
Adds a DataFrame-based
NetTCR.predict_dataframe(...)path that treats each input row as one(peptide, TCR)pair and buildsTCRobjects from canonical CDR columns or caller-providedcdr_colsmappings.Also expands
TCR.from_dictto accept case-insensitivea1..b3/A1..B3aliases and addsTCR.from_seriesfor pandas row inputs.Impact
Callers can score receptor tables without hand-building
TCRobjects per row, while the existingpredict_dataframe(peptides, tcrs)cross-product API remains supported.Validation
pytest tests/test_tcr.py tests/test_nettcr.py -q./lint.sh./test.sh(650 passed, 51 skipped, 2 xfailed)Version
Bumped package version from
3.31.2to3.31.3.